Added deployment output files to the image during build #186
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We require contributors/corporates @begmaroman to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document |
|
We require contributors/corporates @begmaroman to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document |
|
We require contributors/corporates @begmaroman to read our Contributor License Agreement, please check the Individual CLA document/Corporate CLA document |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The image-building process includes several smart contract deployments. Deployed smart contracts have specific addresses that are stored in "docker/deploymentOutput" directory. Meaning each specific image has its own smart contract addresses that should be known by users of this image. Curently, these addresses are not stored anywhere so most likely we lose them and have to create a new image again.
The idea is to include the output file with the addresses of all smart contracts that were deployed during the build of this image into the image and make them accessible via http endpoint.